We are having an issue with Room Mailbox resources in Exchange 2007 and Outlook 2010. We have several Room's in our company and they all work fine, with the permissions as follow: Name Permission Level Default Author Anonymous None I am a part of a "Security Group" that has full access to this Shared Mailbox, so I can view, edit, and change all of the information just fine. Here are the following permissions for the shared mailbox under the Exchange Management Console: Send As Permission: NT AUTHORITY\SELF Full Access Permission: <Our domain>\Exchange Domain Servers <Our domain>\<My security group> NT AUTHORITY\SELF Regular users can view the calendars; however, when they try to Add an appointment to that Room Mailbox it does nothing and a message pops up saying: "Cannot open the free/busy information" and the other Calendar says: "Cannot open this item. Cannot open the free/busy information". The calendars are identical to the other calendars, except for this free/busy information. I cannot find the free/busy permissions in Exchange 2007 for these newly created Room Mailboxes, or even in Outlook 2010. I have already tried: outlook.exe /cleanfreebusy Can anyone explain what is going on? Or does anyone have an idea how to fix this? Thanks, -R-

Update: I have also exported all of the SchemaDefault and Inherited permissions of both Room Mailbox (users) to a text file, and after comparing their Active Directory permissions, they are identical. Is there possibly some other place that could be different? Active Directory permissions are the same, Calendar Properties Permissions are the same, Exchange: Send As Permissions and Full Permissions are the same. Yet the new Room Mailbox Calendar still comes up with: "Cannot open the free/busy information", unless I explicitly add each individual user to the Calendar Properties Permissions.

Here is a script I just created for a client to setup security for shared mailboxes migrated from Domino into Exchange 2010. The part that had be dumbfounded for a while what that normal users not only do not have default rights to read a room, they do not have rights to even view the room's permissions. This is why I run the following for the read-only group. $mbx | Add-MailboxPermission -User $ROname -AccessRights 'ReadPermission' -InheritanceType All Also, you notice I run the loop twice. I did this on purpose so I did not have to specify a domain controller but still allowed time for the groups to be created before trying to use them right away. Full script: $SharedMailbox = Get-Mailbox -Filter 'RecipientTypeDetails -eq "SharedMailbox"' $GroupOU = 'domain.com/Groups' # Create Groups<br/>Foreach ($mbx in $SharedMailbox) { $FAname = "S-" + $mbx.DisplayName + "-FullAccess" $SAname = "S-" + $mbx.DisplayName + "-SendAs" $ROname = "S-" + $mbx.DisplayName + "-ReadOnlyAccess" If(Get-DistributionGroup $FAname -ea SilentlyContinue) { Write-Host "Group $($FAname) already exists" } Else { New-DistributionGroup -Name $FAname -Type 'Security' ` -OrganizationalUnit $GroupOU -SamAccountName $FAname -Alias ($FAname -replace " ") } If(Get-DistributionGroup $SAname -ea SilentlyContinue) { Write-Host "Group $($SAname) already exists" } Else { New-DistributionGroup -Name $SAname -Type 'Security' ` -OrganizationalUnit $GroupOU -SamAccountName $SAname -Alias ($SAname -replace " ") } If(Get-DistributionGroup $ROname -ea SilentlyContinue) { Write-Host "Group $($ROname) already exists" } Else { New-DistributionGroup -Name $ROname -Type 'Security' ` -OrganizationalUnit $GroupOU -SamAccountName $ROname -Alias ($ROname -replace " ") } } Foreach ($mbx in $SharedMailbox) { $FAname = "S-" + $mbx.DisplayName + "-FullAccess" $SAname = "S-" + $mbx.DisplayName + "-SendAs" $ROname = "S-" + $mbx.DisplayName + "-ReadOnlyAccess" # Add permissions $mbx | Add-MailboxPermission -User $FAname -AccessRights 'FullAccess' -InheritanceType All $mbx | Add-ADPermission -User $SAname -ExtendedRights 'Send-as' $mbx | Add-MailboxPermission -User $ROname -AccessRights 'ReadPermission' -InheritanceType All Add-MailboxFolderPermission -Identity "$($mbx.alias):\" -AccessRights 'Reviewer' -User $ROname Add-MailboxFolderPermission -Identity "$($mbx.alias):\Inbox" -AccessRights 'Reviewer' -User $ROname Add-MailboxFolderPermission -Identity "$($mbx.alias):\Calendar" -AccessRights 'Reviewer' -User $ROname Add-MailboxFolderPermission -Identity "$($mbx.alias):\Tasks" -AccessRights 'Reviewer' -User $ROname Add-MailboxFolderPermission -Identity "$($mbx.alias):\Contacts" -AccessRights 'Reviewer' -User $ROname Add-MailboxFolderPermission -Identity "$($mbx.alias):\Deleted Items" -AccessRights 'Reviewer' -User $ROname Add-MailboxFolderPermission -Identity "$($mbx.alias):\Sent Items" -AccessRights 'Reviewer' -User $ROname }<br/> Brian Kronberg, Senior Consultant-UC Practice, CDW. MCITP:Exchange, MCSE:M

Thank you Brian! I appreciate it. I think it is so weird that normal users do not have default rights to read a room, and do not have rights to even view the room's permissions. It sounds like this issue happens with Exchange 2010 as you stated, so I'll have to remember that when we upgrade within the next few months from 07 to 10. Just a little bit frustrating that normal users don't have the permissions, nor the rights to even view. Thank you again.